History / Performance

Data Import History contains a log entry of all data imports or externals that have been run in the system.

  • EDI Import History shows all the EDI orders that were created as a result of EDI Imports. The log also contains information regarding why EDI Imports were not processed correctly.
  • The Link Document History table displays which Link Document attempts have passed or failed. Once the report is run, the system will display the outcome of the link document import attempt as well as the file name.
  • A Trigger is a stored procedure that runs automatically when a row is inserted, updated, or deleted in a table. The Trigger History report displays a log containing the Trigger name, the date and time a Trigger was initiated in the Deacom system, and the result.
  • The Update History form displays the software updates that have been made to the Deacom system. The display includes the time the update was performed, the status of the update, and the change made in the system version.
  • The System Performance report displays information on Deacom performance or errors that the database has experienced including the time and a description of the event. Error reports can be helpful if an error needs to be reported to the Support Team.

System Navigation

  • System > History / Performance

View History / Performance pre-filter

The options available for selection vary depending on the option chosen in the "Type" field of the pre-filter.

Field

Description

Type

Pick list used to select the kind of report to generate. Options are:

  • API
  • Data Import
  • DSD (requires DSD license)
  • eCommerce
  • EDI Import
  • External Program
  • Link Document
  • Scheduled Import
  • Script
  • Sync -allows the user to view all logged information from externals which perform external sync actions. (Added in version 17.03.009) Note: With the addition of this report type, other History/Performance reports no longer display these external sync records in the results.
  • System
  • Trigger
  • Update

Report Type

Pick list used to select the report to run. The options in this field depend on the selection made in the "Type" field above.

  • Set to History, and cannot be changed, when choosing a "Type" of "Data Import," "EDI Import," "External Program," "Link Document," "Trigger," or "Update."
  • Set to Errors, and cannot be changed, when choosing a "Type" of "eCommerce."
  • When selecting a "Type" of "Scheduled Import" the choices will be History or Performance.
  • When selecting a "Type" of "API", the choices will be History or Integration Logging. The Integration Logging report is used in connection with the Avalara Tax API when the "Enable Client Side Logging for Tax APIs" flag is checked in Sales > Options.
  • When using a "Type" of "System," the choices will be Errors, Performance, or Security.

Start/End

Date The date range on which the report will filter. This will default to today's date. Entering dates is helpful for customers that process large amounts of EDI transactions or Triggers.

Outcome

Pick list used to select the kind of outcomes to search. Options are: All Failure Success Available when selecting a "Type" of "EDI Import", "Link Document", and “Trigger”.

Record,

EDI Import,

External Program,

Link Document, Scheduled Import,

Trigger,

or API Profile

Search field used to select an appropriate value based on the Type selected.

  • This field is set to Record, and cannot be changed when choosing a "Type" of "Data Import," "System," and "Update."
  • Set to "EDI Import," "External Program," "Link Document," "Scheduled Import," or "Trigger" when these Types are selected on the pre-filter.
  • "API Profile" - select a profile to associate with the logged information.
    • Only available when selecting a Type of "Sync".
    • Only logging data corresponding to the chosen API Profile is shown in this case. Useful for providing clarity on which API actions are associated with specific sync events.
    • Used in connection with the Commerce Suite AP API. and the “CommerceSuiteSystemSync” external program. (Added in version 17.03.009)
    • Note: Selecting an API Profile when running the "Sync" report is not required. If a profile is not selected, the system will display all sync logging events that have ever occurred in the system.

View Data Import History report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "Data Import".

Note: The security, "Tools -- delete data imports" is available. If this security is set to yes, the delete button "X" will be visible on the toolbar and the user will be able to delete the selected import load. Users will be presented with a list of the records that will be deleted. This only applies prior to being "Live" in Deacom.

Column

Description

Date

The date the data import or external was run.

Time

The exact time in that the data import or external was run.

Description

Only applicable for data imports. The description of the data import.

Table

Only applicable for data imports. The Deacom database table into which the data was imported.

File

The source file or files used in the data import or the name of the external that was run.

Profile

Only applicable for externals. The ID of the User who ran the external.

View EDI Import History report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "EDI History."

Column

Description

Date

Date the EDI Import attempt occurred.

Time

Time the EDI Import attempt occurred.

EDI Import

The EDI Import that was executed. Outcome The outcome of executing the EDI Import (Success or Failure).

File

The name of the File that failed to import.

Line

Line that caused the EDI Import to fail.

Message

If Success, lists the order numbers that were created or updated. If Failure, details the Reason the EDI Import failed.

External Programs History report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "External Program."

Column

Description

External Program

The External that was executed.

Date

Date the External run was attempted.

Time

Time the External run was attempted.

Stack

Displays details regarding the parameters used in execution of the External.

Message

Displays information the program logs regarding execution of the External. Useful for diagnostics.

Level

Displays ERROR, INFO, or WARN application constants to help log the issue or message encountered.

  • ERROR might describe things that have broken execution of the external
  • WARN might be lines that were skipped due to formatting errors
  • INFO will display general processing information, such as orders imported.

Link Document Profiles History report

Opened via the "View" button on the on the View History / Performance pre-filter when "Type" is set to "Link Document."

Column

Description

Date

Date the link document attempt occurred.

Time

Time the link document attempt occurred.

Link Doc Import

The Link Document that was executed.

Outcome

The outcome of executing the Link Document.

File

The name of the File that failed to link.

Message

Reason indicating Link Document failure

Scheduled Import History / Performance report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "Scheduled Import".

Column

Description

Scheduled Import

Name of the data import.

Date

Date the import attempt occurred.

Time

Time the import attempt occurred.

Duration

Only visible on the Scheduled Import Performance report, displays the duration of the import.

System Performance / Errors report

System Errors report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "System" and "Report Type" is set to "Errors."

Column

Description

Date

Date the error occurred.

Time

Time the error occurred. User User who received the error.

Error

Error number.

Line

Line on which the error occurred. Build Deacom build number in which the error occurred.

Program

Program running when error occurred.

Stack

Stack information (for use by developers).

System Performance report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "System" and "Report Type" is set to "Performance."

Column

Description

Date

Date the action occurred.

Time

Time the action occurred.

Grid Layout

Grid Layout pertaining to the action.

Grid Filters

Grid filters used during the action.

Duration

Time in seconds to generate the grid.

User Count

 

Trigger History report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "Trigger."

Trigger History report buttons

Button

Description

Reprocess

If clicked, offers users the option to reprocess the highlighted trigger, weather it has failed or not.

  • Useful when users wish to reprocess successful triggers or when a failure occurs, such as when the Deacom automation service goes down (such as during a power outage) and triggers need to be re-sent without un-doing/re-doing the underlying Deacom transaction.

Column

Description

Date

Date the Trigger attempt occurred.

Time

Time the Trigger attempt occurred.

Trigger

Trigger Name.

Message

Trigger Result.

Processed

Indicates "Yes" if Trigger was successfully processed.

Update History report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "Update".

Column

Description

Date

Date update was applied.

Start Time

Time update started.

End Time

Time update ended.

Minutes

The number of minutes it took for update to complete.

Result

The result of installing the update. If the update failed, a reason is provided.

Start Version

Version of the software before the update.

End Version

Version of the software after the update.

System Locks report

Opened via the "View" button on the View History/Performance pre-filter when "Type" is set to "System" and "Report Type" is set to "Record Contention".

The "Release Record" button at the top of the report will allow a user to release the highlighted lock.

Column

Description

Date Date the lock was applied.
Time Time the lock was applied.
Action Action the user was taking before the lock was applied.
User The user who has the lock applied.
Table The table on which the lock occurred.
Record Record of the lock.
Critical

True of False if it is a critical lock.

  • A critical lock can not be released via the Release Record button for non-admin users.

eCommerce Error Log report

Opened via the "View" button on the View History / Performance pre-filter when "Type" is set to "eCommerce".

Column

Description

Site Name

Name or IP address of the eCommerce Site where the error was logged.

Stack

Useful information for Deacom development when determining the cause of the error.

Exception

Readable text describing what the error is.

Related Pages